Committed to connecting the world

  •  
wtisd

ITU-T work programme

Home : ITU-T Home : ITU-T Work Programme : G.8011/Y.1307     
  ITU-T A.5 justification information for referenced document MEF 47 in draft G.8011/Y.1307
1. Clear description of the referenced document:
Name: MEF 47
Title: Carrier Ethernet Services for Cloud Implementation Agreement This document identifies the requirements for MEF Ethernet Services and MEF External Interfaces (EIs such as UNIs) as well as a management interface for use in support of Cloud Services. This support includes elastic behavior of Ethernet Service attributes that can be modified during the lifetime of the service. Support for Cloud Services falls into two broad categories: 1) interconnection of a Cloud Provider's data centers (referred to as Data Center Interconnect - DCI), and 2) interconnection of Cloud Consumers (e.g. enterprises) and Cloud Provider data centers (referred to as Data Center Access - DCA). The services and requirements in this Implementation Agreement are based on the services defined in MEF 6.2 and the attributes defined in MEF 10.3 and this IA. Support of Cloud Services is addressed for a single Cloud Provider (CP) using one or more Carrier Ethernet Networks (CENs) and point-to-point Ethernet Services.
2. Status of approval:
Approved in October 2014
3. Justification for the specific reference:
Elastic Ethernet services that allow modification of service attributes related to CoS, in support of cloud services, are specified in MEF 47, and forma a basis for this Recommendation
4. Current information, if any, about IPR issues:
No known issues.
5. Other useful information describing the "Quality" of the document:
Commonly referenced all over the world for metro Ethernet services.
6. The degree of stability or maturity of the document:
Commonly referenced all over the world for metro Ethernet services.
7. Relationship with other existing or emerging documents:
8. Any explicit references within that referenced document should also be listed:
[1] Internet Engineering Task Force RFC 2119. Key words for use in RFCs to Indicate Requirement Levels, March 1997./
[2] Special Publication 800-145, The NIST Definition of Cloud Computing, September 2011, http://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf/
[3] Special Publication 500-292, NIST Cloud Computing Reference Architecture, September 2011, http://www.nist.gov/customcf/get_pdf.cfm?pub_id=909505/
[4] MEF 4, “Metro Ethernet Network Architecture Framework - Part 1: Generic Framework”, May 2004./
[5] MEF 6.2, Ethernet Services Definitions, August 2014./
[6] MEF 10.3, Ethernet Services Attributes Phase 3, October 2013./
[7] MEF 12.2, “Carrier Ethernet Network Architecture Framework Part 2: Ethernet Services Layer”, May 2014./
[8] MEF 13, “User Network Interface (UNI) Type 1 Implementation Agreement”, November, 2005./
[9] MEF 17, "Service OAM Requirements & Framework – Phase 1", April 2007./
[10] MEF 20, "User Network Interface (UNI) Type 2 Implementation Agreement", July 2008./
[11] MEF 23.1, “Carrier Ethernet Class of Service – Phase 2”, January 2012./
[12] MEF 26.1, "External Network Network Interface (ENNI) – Phase 2", January 2012./
[13] MEF 30.1, "Service OAM Fault Management Implementation Agreement: Phase 2", April 2013./
[14] MEF 33, “Ethernet Access Services Definition”, January 2012./
[15] MEF 35, “Service OAM Performance Monitoring Implementation Agreement”, April 2012./
[16] IEEE Std 802.1AX™ – 2008, IEEE Standard for Local and metropolitan area networks – Link Aggregation, November 2008.
9. Qualification of MEF:
The MEF was recognized under the provisions of ITU-T Recommendation A.5 on 24 September 2002. Qualifying information is on file with TSB.
9.5     The IPR policy of the MEF may be found in Article 10 of the MEF Bylaws which are available on the MEF public WEB site metroethernetforum.org.
9.6     All MEF Technical Specifications, Implementation Agreements, and Test Specifications are approved by an electronic letter ballot of all MEF members. For a MEF document to pass an electronic letter ballot at least a quorum of members (defined by the MEF bylaws as 1/3 of the MEF membership) must vote Yes or No. In addition, of the Yes plus No votes at least 75% of the votes must be Yes.
9.7     All published MEF documents are available for download free of charge in PDF or WORD format from the MEF public WEB site www.metroethernetforum.org .
9.8     Each revision of a given MEF document has a different MEF number.
10. Other (for any supplementary information):
None
Note: This form is based on Recommendation ITU-T A.5